Release 10.1A: OpenEdge Application Server:
Developing AppServer Applications

About the Debugger window

When you are using distributed debugging, the Debugger window and the procedure call stack help orient you to the procedures available to debug. For example, the title bar of the Debugger Listing Panel changes as you change the procedures that you are debugging. Table 5–1 indicates the dynamic information changes that occur in the title bar.

Table 5–1: Content of the Debugger Listing Panel title bar 

When you are stepping through a...	Then the title bar reads...
Local procedure, such as example.p.	example.p (LOCAL).
Remote procedure, such as remote.p, on an AppServer agent whose server handle’s NAME attribute is RemoteServer1.	remote.p (ON SERVER RemoteServer1).
Remote procedure, such as distant.p, on an AppServer agent whose server handle’s NAME attribute is RemoteServer2, which was run from a procedure on RemoteServer1 (RemoteServer2 is an AppServer agent once removed from the root client application.)	distant.p (ON SERVER RemoteServer2 via RemoteServer1).

The procedure call stack reflects the entire call stack for the distributed application.

For example, if example.p, line 4, runs remote.p, and remote.p, line 3 runs distant.p and you are stepping through line 17, the procedure stack displays the following information:

example.p():4 remote.p(...):3 ON SERVER RemoteServer1 distant.p(...):17 ON SERVER RemoteServer2 Via RemoteServer1

Note: Line numbers do not appear in local client procedures.

Note that when using distributed debugging, the root client application must run in an environment that supports the Debugger. However, you can step into a procedure running on an AppServer installed through OpenEdge Client Networking that does not itself contain the Debugger.